Detailed eoms #273
Closed
Detailed eoms #273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Peter230655
added a commit
to Peter230655/opty
that referenced
this pull request
Jan 28, 2025
|
This was replaced by PR #310, as this one cannot pass the doc/readthedoc.... test and I did not know how to fix it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At present all EoM violations a printed in one plot when using plot_constraint_violations(..). There may be occasions when one would want to see each eom violation in a separate plot.
I added an optional keyword detailed_eoms with default value False. If set to True, each eom violation will be put in a separate plot, If not set, or set to False, all is like it has been, that is all EoM violations in one plot.